docs(infralifecycle): suggestion for section content - #2214
Merged
kfaseela merged 6 commits intoJul 10, 2026
Merged
Conversation
This commit is a suggestion for the section for On-Demand vs. Continuously Reconciled. Signed-off-by: Roberth Strand <roberth@pm.me>
github-actions
Bot
added
needs-triage
bschaatsbergen
approved these changes
Jul 1, 2026
thschue
requested changes
Jul 2, 2026
thschue
left a comment
thschue
left a comment
Contributor
There was a problem hiding this comment.
Good work!
Made some proposals to remove the "you" form there.
Co-authored-by: Thomas Schuetz <38893055+thschue@users.noreply.github.com> Signed-off-by: Roberth Strand <me@robstr.dev>
Co-authored-by: Thomas Schuetz <38893055+thschue@users.noreply.github.com> Signed-off-by: Roberth Strand <me@robstr.dev>
Co-authored-by: Thomas Schuetz <38893055+thschue@users.noreply.github.com> Signed-off-by: Roberth Strand <me@robstr.dev>
kfaseela
reviewed
Jul 9, 2026
|
|
||
| These are two paradigms in lifecycle management that are fundamental opposites. On the one side, changes can be triggered by a person or external system, the other is where the system itself can reconcile any changes by observing a source. The first can be done through a portal, CLI, or scripts, while the other requires that you install and maintain a set of agents whose behavior is defined by configuration or policy. | ||
|
|
||
| When infrastructure is managed with on-demand solutions like scripts, either manually or through an automation pipeline, one of the benefits gained is immediate feedback. With a reconciliation process, one can rely on eventual consistency, which requires all changes to happen at the source. The GitOps principles call this the “desired state” and it should always be what the system tries to adhere to. This means that a continuously reconciled system is self-healing, while any on-demand model has no such guarantee. |
Contributor
There was a problem hiding this comment.
Nit: "immediate feedback" vs "eventual consistency" - Would it be better to frame around "operator-initiated" vs "system-driven convergence" instead ?
kfaseela
reviewed
Jul 9, 2026
Signed-off-by: Roberth Strand <roberth@pm.me>
Signed-off-by: Roberth Strand <roberth@pm.me>
Contributor
|
LGTM.. leaving to @thschue for review as he requested changes |
Member
Author
|
Not sure who is left to approve and merge (@cncf/tag-infrastructure-leads ?) but I will start on a second section today :) |
kfaseela
approved these changes
Jul 10, 2026
Contributor
|
Merging since tag-infra-leads have already approved :) |
roberthstrand
deleted the
feat/infra-lifecycle-on-demand-vs-continuous-reconciliation
branch
July 10, 2026 12:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit is a suggestion for the section for On-Demand vs. Continuously Reconciled.